Method and system for interaction servicing with embeddable ribbon display

ABSTRACT

A system and a method for managing contact center functionality are provided. The method includes: receiving, from a servicing application, a request for a web application that implements a plurality of contact center functions; integrating the web application into the servicing application; and displaying a ribbon that includes information that relates to each of the plurality of contact center functions. The ribbon may be embeddable in a user interface screen of the servicing application.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 63/036,752, filed Jun. 9, 2020, which is hereby incorporated by reference in its entirety.

This application is being filed concurrently on Nov. 4, 2020 with each of U.S. patent application Ser. No. 17/089,275, entitled “Method and System for Interaction Servicing”; U.S. patent application Ser. No. 17/089,305, entitled “Method and System for Interaction Servicing with Embeddable Ribbon Display”; U.S. patent application Ser. No. 17/089,302, entitled “Method and System for Resolving Producer and Consumer Affinities in Interaction Servicing”; U.S. patent application Ser. No. 17/089,311, entitled “Method and System for Providing Resiliency in Interaction Servicing”; U.S. patent application Ser. No. 17/089,061, entitled “Method and System for Providing Resiliency in Interaction Servicing Across Data Centers”; U.S. patent application Ser. No. 17/089,093, entitled “Method and System for Providing Resiliency in Interaction Servicing Across Data Centers”; and U.S. patent application Ser. No. 17/089,145, entitled “Method and System for Providing High Efficiency, Bidirectional Messaging for Low Latency Applications,” the contents of each of which is hereby incorporated by reference in its respective entirety.

BACKGROUND 1. Field of the Disclosure

This technology generally relates to methods and systems for performing customer service interactions, and more particularly to methods and systems for integrating and streamlining large number of customer service interactions to ensure efficient and accurate interaction servicing results.

2. Background Information

For a large corporate organization that has many customers, customer service is an important aspect of the business operation. Customers typically expect service requests to be handled in a timely and accurate manner, and if the corporate organization fails to provide such customer service, there may be a negative effect on the reputation of that organization.

Many customer service requests are performed online via the Internet. For such requests, it is important that the request be assessed and routed to the correct entity within the corporate organization, together with all of the relevant information that will be needed by the entity that will handle the request. However, the proper routing and handling of such requests may be complicated when the number of requests is large and the size of the corporate organization is large.

Accordingly, there is a need for a tool that integrates and streamlines the processing of customer service interactions in order to ensure efficient and accurate handling and resolution thereof.

SUMMARY

The present disclosure, through one or more of its various aspects, embodiments, and/or specific features or sub-components, provides, inter alia, various systems, servers, devices, methods, media, programs, and platforms for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results.

According to an aspect of the present disclosure, a method for managing contact center interactions is provided. The method is implemented by at least one processor. The method includes: receiving, by the at least one processor from a servicing application, a request for a web application that implements a plurality of contact center functions; integrating, by the at least one processor, the web application into the servicing application; and displaying, by the at least one processor, a ribbon that includes information that relates to each of the plurality of contact center functions.

The method may further include embedding the ribbon in a user interface screen of the servicing application.

The ribbon may be displayed in a section of the user interface screen that is positioned adjacent to a task bar of the servicing application.

The plurality of contact center functions may include at least two from among a user status function that maintains an agent state and a channel activity state, a profile function that maintains agent profile information, a discovery function that provides information relating to available services and corresponding Uniform Resource Locators (URLs), a call function that relates to incoming and outgoing telephone calls, a notification function that establishes a web socket for events, and a queue function that relates to queue statistics.

Each of the plurality of contact center functions may be implemented as a respective cloud native microservice.

The web application may include a JavaScript software development kit that connects each respective cloud native microservice to a transaction processing application.

The method may further include using the JavaScript software development kit to manage connectivity to cloud microservices and to propagate received events to the servicing application.

The method may further include: activating at least one feature that corresponds to the received event; and displaying, in the ribbon, a respective image that relates to each of the activated at least one feature.

When the received event is an incoming call, the method may further include using the JavaScript software development kit to provide metadata associated with the call to the servicing application.

According to another aspect of the present disclosure, a computing apparatus for managing contact center interactions is provided. The computing apparatus includes a processor, a memory, a display, and a communication interface coupled to each of the processor, the memory, and the display. The processor is configured to: receive, from a servicing application, a request for a web application that implements a plurality of contact center functions; integrate the web application into the servicing application; and display, on the display, a ribbon that includes information that relates to each of the plurality of contact center functions.

The processor may be further configured to embed the ribbon in a user interface screen of the servicing application.

The ribbon may be displayed in a section of the user interface screen that is positioned adjacent to a task bar of the servicing application.

The plurality of contact center functions may include at least two from among a user status function that maintains an agent state and a channel activity state, a profile function that maintains agent profile information, a discovery function that provides information relating to available services and corresponding Uniform Resource Locators (URLs), a call function that relates to incoming and outgoing telephone calls, a notification function that establishes a web socket for events, and a queue function that relates to queue statistics.

Each of the plurality of contact center functions may be implemented as a respective cloud native microservice.

The web application may include a JavaScript software development kit that connects each respective cloud native microservice to a transaction processing application.

The processor may be further configured to use the JavaScript software development kit to manage connectivity to cloud microservices and to propagate received events to the servicing application.

The processor may be further configured to: activate at least one feature that corresponds to the received event; and display, in the ribbon, a respective image that relates to each of the activated at least one feature.

When the received event is an incoming call, the processor may be further configured to use the JavaScript software development kit to provide metadata associated with the call to the servicing application.

According to yet another aspect of the present disclosure, a non-transitory computer readable storage medium storing instructions for managing contact center interactions is provided. The storage medium includes executable code which, when executed by at least one processor, causes the at least one processor to receive, from a servicing application, a request for a web application that implements a plurality of contact center functions; integrate the web application into the servicing application; and display a ribbon that includes information that relates to each of the plurality of contact center functions.

When executed by the at least one processor, the executable code may further cause the at least one processor to embed the ribbon in a user interface screen of the servicing application.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is further described in the detailed description which follows, in reference to the noted plurality of drawings, by way of non-limiting examples of preferred embodiments of the present disclosure, in which like characters represent like elements throughout the several views of the drawings.

FIG. 1 illustrates an exemplary computer system.

FIG. 2 illustrates an exemplary diagram of a network environment.

FIG. 3 shows an exemplary system for implementing a method for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results.

FIG. 4 is a flowchart of an exemplary process for implementing a method for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results.

FIG. 5 is a first screenshot that illustrates a user interface for handling a customer interaction, according to an exemplary embodiment.

FIG. 6 is a second screenshot that illustrates customer identification information that is displayable on the user interface for handling a customer interaction, according to an exemplary embodiment.

FIG. 7 is a diagram that illustrates a plurality of microservices and corresponding routing paths for implementing a method for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results, according to an exemplary embodiment.

FIG. 8 is a diagram that illustrates an anatomy of a ribbon that is embeddable in a user interface of a servicing application, according to an exemplary embodiment.

FIG. 9 is a diagram of a ribbon sequence of initializing and activating servicing fabric microservices, according to an exemplary embodiment.

FIG. 10 is a diagram of an integration sequence for integrating a ribbon with a servicing application, according to an exemplary embodiment.

DETAILED DESCRIPTION

Through one or more of its various aspects, embodiments and/or specific features or sub-components of the present disclosure, are intended to bring out one or more of the advantages as specifically described above and noted below.

The examples may also be embodied as one or more non-transitory computer readable media having instructions stored thereon for one or more aspects of the present technology as described and illustrated by way of the examples herein. The instructions in some examples include executable code that, when executed by one or more processors, cause the processors to carry out steps necessary to implement the methods of the examples of this technology that are described and illustrated herein.

FIG. 1 is an exemplary system for use in accordance with the embodiments described herein. The system 100 is generally shown and may include a computer system 102, which is generally indicated.

The computer system 102 may include a set of instructions that can be executed to cause the computer system 102 to perform any one or more of the methods or computer-based functions disclosed herein, either alone or in combination with the other described devices. The computer system 102 may operate as a standalone device or may be connected to other systems or peripheral devices. For example, the computer system 102 may include, or be included within, any one or more computers, servers, systems, communication networks or cloud environment. Even further, the instructions may be operative in such cloud-based computing environment.

In a networked deployment, the computer system 102 may operate in the capacity of a server or as a client user computer in a server-client user network environment, a client user computer in a cloud computing environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 102, or portions thereof, may be implemented as, or incorporated into, various devices, such as a personal computer, a tablet computer, a set-top box, a personal digital assistant, a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless smart phone, a personal trusted device, a wearable device, a global positioning satellite (GPS) device, a web appliance, a device that is running the Apple iOS operating system, a device that is running the Android operating system, a device that is capable of running a web browser to connect to the Internet, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single computer system 102 is illustrated, additional embodiments may include any collection of systems or sub-systems that individually or jointly execute instructions or perform functions. The term “system” shall be taken throughout the present disclosure to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.

As illustrated in FIG. 1, the computer system 102 may include at least one processor 104. The processor 104 is tangible and non-transitory. As used herein, the term “non-transitory” is to be interpreted not as an eternal characteristic of a state, but as a characteristic of a state that will last for a period of time. The term “non-transitory” specifically disavows fleeting characteristics such as characteristics of a particular carrier wave or signal or other forms that exist only transitorily in any place at any time. The processor 104 is an article of manufacture and/or a machine component. The processor 104 is configured to execute software instructions in order to perform functions as described in the various embodiments herein. The processor 104 may be a general-purpose processor or may be part of an application specific integrated circuit (ASIC). The processor 104 may also be a microprocessor, a microcomputer, a processor chip, a controller, a microcontroller, a digital signal processor (DSP), a state machine, or a programmable logic device. The processor 104 may also be a logical circuit, including a programmable gate array (PGA) such as a field programmable gate array (FPGA), or another type of circuit that includes discrete gate and/or transistor logic. The processor 104 may be a central processing unit (CPU), a graphics processing unit (GPU), or both Additionally, any processor described herein may include multiple processors, parallel processors, or both. Multiple processors may be included in, or coupled to, a single device or multiple devices.

The computer system 102 may also include a computer memory 106. The computer memory 106 may include a static memory, a dynamic memory, or both in communication. Memories described herein are tangible storage mediums that can store data as well as executable instructions and are non-transitory during the time instructions are stored therein. Again, as used herein, the term “non-transitory” is to be interpreted not as an eternal characteristic of a state, but as a characteristic of a state that will last for a period of time. The term “non-transitory” specifically disavows fleeting characteristics such as characteristics of a particular carrier wave or signal or other forms that exist only transitorily in any place at any time. The memories are an article of manufacture and/or machine component. Memories described herein are computer-readable mediums from which data and executable instructions can be read by a computer. Memories as described herein may be random access memory (RAM), read only memory (ROM), flash memory, electrically programmable read only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, a hard disk, a cache, a removable disk, tape, compact disk read only memory (CD-ROM), digital versatile disk (DVD), floppy disk, blu-ray disk, or any other form of storage medium known in the art. Memories may be volatile or non-volatile, secure and/or encrypted, unsecure and/or unencrypted. Of course, the computer memory 106 may comprise any combination of memories or a single storage.

The computer system 102 may further include a display 108, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a plasma display, or any other type of display, examples of which are well known to skilled persons.

The computer system 102 may also include at least one input device 110, such as a keyboard, a touch-sensitive input screen or pad, a speech input, a mouse, a remote control device having a wireless keypad, a microphone coupled to a speech recognition engine, a camera such as a video camera or still camera, a cursor control device, a global positioning system (GPS) device, an altimeter, a gyroscope, an accelerometer, a proximity sensor, or any combination thereof. Those skilled in the art appreciate that various embodiments of the computer system 102 may include multiple input devices 110. Moreover, those skilled in the art further appreciate that the above-listed, exemplary input devices 110 are not meant to be exhaustive and that the computer system 102 may include any additional, or alternative, input devices 110.

The computer system 102 may also include a medium reader 112 which is configured to read any one or more sets of instructions, e.g. software, from any of the memories described herein. The instructions, when executed by a processor, can be used to perform one or more of the methods and processes as described herein. In a particular embodiment, the instructions may reside completely, or at least partially, within the memory 106, the medium reader 112, and/or the processor 110 during execution by the computer system 102.

Furthermore, the computer system 102 may include any additional devices, components, parts, peripherals, hardware, software or any combination thereof which are commonly known and understood as being included with or within a computer system, such as, but not limited to, a network interface 114 and an output device 116. The output device 116 may be, but is not limited to, a speaker, an audio out, a video out, a remote-control output, a printer, or any combination thereof.

Each of the components of the computer system 102 may be interconnected and communicate via a bus 118 or other communication link. As illustrated in FIG. 1, the components may each be interconnected and communicate via an internal bus. However, those skilled in the art appreciate that any of the components may also be connected via an expansion bus. Moreover, the bus 118 may enable communication via any standard or other specification commonly known and understood such as, but not limited to, peripheral component interconnect, peripheral component interconnect express, parallel advanced technology attachment, serial advanced technology attachment, etc.

The computer system 102 may be in communication with one or more additional computer devices 120 via a network 122. The network 122 may be, but is not limited to, a local area network, a wide area network, the Internet, a telephony network, a short-range network, or any other network commonly known and understood in the art. The short-range network may include, for example, Bluetooth, Zigbee, infrared, near field communication, ultraband, or any combination thereof. Those skilled in the art appreciate that additional networks 122 which are known and understood may additionally or alternatively be used and that the exemplary networks 122 are not limiting or exhaustive. Also, while the network 122 is illustrated in FIG. 1 as a wireless network, those skilled in the art appreciate that the network 122 may also be a wired network.

The additional computer device 120 is illustrated in FIG. 1 as a personal computer. However, those skilled in the art appreciate that, in alternative embodiments of the present application, the computer device 120 may be a laptop computer, a tablet PC, a personal digital assistant, a mobile device, a palmtop computer, a desktop computer, a communications device, a wireless telephone, a personal trusted device, a web appliance, a server, a device that is running the Apple iOS operating system, a device that is running the Android operating system, a device that is capable of running a web browser to connect to the Internet. or any other device that is capable of executing a set of instructions, sequential or otherwise, that specify actions to be taken by that device. Of course, those skilled in the art appreciate that the above-listed devices are merely exemplary devices and that the device 120 may be any additional device or apparatus commonly known and understood in the art without departing from the scope of the present application. For example, the computer device 120 may be the same or similar to the computer system 102. Furthermore, those skilled in the art similarly understand that the device may be any combination of devices and apparatuses.

Of course, those skilled in the art appreciate that the above-listed components of the computer system 102 are merely meant to be exemplary and are not intended to be exhaustive and/or inclusive. Furthermore, the examples of the components listed above are also meant to be exemplary and similarly are not meant to be exhaustive and/or inclusive.

In accordance with various embodiments of the present disclosure, the methods described herein may be implemented using a hardware computer system that executes software programs. Further, in an exemplary, non-limited embodiment, implementations can include distributed processing, component/object distributed processing, and parallel processing. Virtual computer system processing can be constructed to implement one or more of the methods or functionalities as described herein, and a processor described herein may be used to support a virtual processing environment.

As described herein, various embodiments provide optimized methods and systems for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results.

Referring to FIG. 2, a schematic of an exemplary network environment 200 for implementing a method for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results is illustrated. In an exemplary embodiment, the method is executable on any networked computer platform, such as, for example, a personal computer (PC), a device that is running the Apple iOS operating system, a device that is running the Android operating system, or a device that is capable of running a web browser to connect to the Internet.

The method for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results may be implemented by an Interaction Servicing Fabric (ISF) device 202. The ISF device 202 may be the same or similar to the computer system 102 as described with respect to FIG. 1. The ISF device 202 may store one or more applications that can include executable instructions that, when executed by the ISF device 202, cause the ISF device 202 to perform actions, such as to transmit, receive, or otherwise process network messages, for example, and to perform other actions described and illustrated below with reference to the figures. The application(s) may be implemented as modules or components of other applications. Further, the application(s) can be implemented as operating system extensions, modules, plugins, or the like.

Even further, the application(s) may be operative in a cloud-based computing environment. The application(s) may be executed within or as virtual machine(s) or virtual server(s) that may be managed in a cloud-based computing environment. Also, the application(s), and even the ISF device 202 itself, may be located in virtual server(s) running in a cloud-based computing environment rather than being tied to one or more specific physical network computing devices. Also, the application(s) may be running in one or more virtual machines (VMs) executing on the ISF device 202. Additionally, in one or more embodiments of this technology, virtual machine(s) running on the ISF device 202 may be managed or supervised by a hypervisor.

In the network environment 200 of FIG. 2, the ISF device 202 is coupled to a plurality of server devices 204(1)-204(n) that hosts a plurality of databases 206(1)-206(n), and also to a plurality of client devices 208(1)-208(n) via communication network(s) 210. A communication interface of the ISF device 202, such as the network interface 114 of the computer system 102 of FIG. 1, operatively couples and communicates between the ISF device 202, the server devices 204(1)-204(n), and/or the client devices 208(1)-208(n), which are all coupled together by the communication network(s) 210, although other types and/or numbers of communication networks or systems with other types and/or numbers of connections and/or configurations to other devices and/or elements may also be used.

The communication network(s) 210 may be the same or similar to the network 122 as described with respect to FIG. 1, although the ISF device 202, the server devices 204(1)-204(n), and/or the client devices 208(1)-208(n) may be coupled together via other topologies. Additionally, the network environment 200 may include other network devices such as one or more routers and/or switches, for example, which are well known in the art and thus will not be described herein. This technology provides a number of advantages including methods, non-transitory computer readable media, and ISF devices that efficiently implement methods and systems for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results.

By way of example only, the communication network(s) 210 may include local area network(s) (LAN(s)) or wide area network(s) (WAN(s)), and can use TCP/IP over Ethernet and industry-standard protocols, although other types and/or numbers of protocols and/or communication networks may be used. The communication network(s) 210 in this example may employ any suitable interface mechanisms and network communication technologies including, for example, teletraffic in any suitable form (e.g., voice, modem, and the like), Public Switched Telephone Network (PSTNs), Ethernet-based Packet Data Networks (PDNs), combinations thereof, and the like.

The ISF device 202 may be a standalone device or integrated with one or more other devices or apparatuses, such as one or more of the server devices 204(1)-204(n), for example. In one particular example, the ISF device 202 may include or be hosted by one of the server devices 204(1)-204(n), and other arrangements are also possible. Moreover, one or more of the devices of the ISF device 202 may be in a same or a different communication network including one or more public, private, or cloud networks, for example.

The plurality of server devices 204(1)-204(n) may be the same or similar to the computer system 102 or the computer device 120 as described with respect to FIG. 1, including any features or combination of features described with respect thereto. For example, any of the server devices 204(1)-204(n) may include, among other features, one or more processors, a memory, and a communication interface, which are coupled together by a bus or other communication link, although other numbers and/or types of network devices may be used. The server devices 204(1)-204(n) in this example may process requests received from the ISF device 202 via the communication network(s) 210 according to the HTTP-based and/or JavaScript Object Notation (JSON) protocol, for example, although other protocols may also be used.

The server devices 204(1)-204(n) may be hardware or software or may represent a system with multiple servers in a pool, which may include internal or external networks. The server devices 204(1)-204(n) hosts the databases 206(1)-206(n) that are configured to store data that relates to user requests, identification information that relates to individual users, and microservices that are used for resolving user requests.

Although the server devices 204(1)-204(n) are illustrated as single devices, one or more actions of each of the server devices 204(1)-204(n) may be distributed across one or more distinct network computing devices that together comprise one or more of the server devices 204(1)-204(n). Moreover, the server devices 204(1)-204(n) are not limited to a particular configuration. Thus, the server devices 204(1)-204(n) may contain a plurality of network computing devices that operate using a master/slave approach, whereby one of the network computing devices of the server devices 204(1)-204(n) operates to manage and/or otherwise coordinate operations of the other network computing devices.

The server devices 204(1)-204(n) may operate as a plurality of network computing devices within a cluster architecture, a peer-to peer architecture, virtual machines, or within a cloud architecture, for example. Thus, the technology disclosed herein is not to be construed as being limited to a single environment and other configurations and architectures are also envisaged.

The plurality of client devices 208(1)-208(n) may also be the same or similar to the computer system 102 or the computer device 120 as described with respect to FIG. 1, including any features or combination of features described with respect thereto. For example, the client devices 208(1)-208(n) in this example may include any type of computing device that can interact with the ISF device 202 via communication network(s) 210. Accordingly, the client devices 208(1)-208(n) may be mobile computing devices, desktop computing devices, laptop computing devices, tablet computing devices, virtual machines (including cloud-based computers), or the like, that host chat, e-mail, or voice-to-text applications, for example. In an exemplary embodiment, at least one client device 208 is a wireless mobile communication device, i.e., a smart phone.

The client devices 208(1)-208(n) may run interface applications, such as standard web browsers or standalone client applications, which may provide an interface to communicate with the ISF device 202 via the communication network(s) 210 in order to communicate user requests and information. The client devices 208(1)-208(n) may further include, among other features, a display device, such as a display screen or touchscreen, and/or an input device, such as a keyboard, for example.

Although the exemplary network environment 200 with the ISF device 202, the server devices 204(1)-204(n), the client devices 208(1)-208(n), and the communication network(s) 210 are described and illustrated herein, other types and/or numbers of systems, devices, components, and/or elements in other topologies may be used. It is to be understood that the systems of the examples described herein are for exemplary purposes, as many variations of the specific hardware and software used to implement the examples are possible, as will be appreciated by those skilled in the relevant art(s).

One or more of the devices depicted in the network environment 200, such as the ISF device 202, the server devices 204(1)-204(n), or the client devices 208(1)-208(n), for example, may be configured to operate as virtual instances on the same physical machine. In other words, one or more of the ISF device 202, the server devices 204(1)-204(n), or the client devices 208(1)-208(n) may operate on the same physical device rather than as separate devices communicating through communication network(s) 210. Additionally, there may be more or fewer ISF devices 202, server devices 204(1)-204(n), or client devices 208(1)-208(n) than illustrated in FIG. 2.

In addition, two or more computing systems or devices may be substituted for any one of the systems or devices in any example. Accordingly, principles and advantages of distributed processing, such as redundancy and replication also may be implemented, as desired, to increase the robustness and performance of the devices and systems of the examples. The examples may also be implemented on computer system(s) that extend across any suitable network using any suitable interface mechanisms and traffic technologies, including by way of example only teletraffic in any suitable form (e.g., voice and modem), wireless traffic networks, cellular traffic networks, Packet Data Networks (PDNs), the Internet, intranets, and combinations thereof.

The ISF device 202 is described and illustrated in FIG. 3 as including an interaction services routing and handling module 302, although it may include other rules, policies, modules, databases, or applications, for example. As will be described below, the interaction services routing and handling module 302 is configured to implement a method for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results.

An exemplary process 300 for implementing a mechanism for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results by utilizing the network environment of FIG. 2 is illustrated as being executed in FIG. 3. Specifically, a first client device 208(1) and a second client device 208(2) are illustrated as being in communication with ISF device 202. In this regard, the first client device 208(1) and the second client device 208(2) may be “clients” of the ISF device 202 and are described herein as such. Nevertheless, it is to be known and understood that the first client device 208(1) and/or the second client device 208(2) need not necessarily be “clients” of the ISF device 202, or any entity described in association therewith herein.

Any additional or alternative relationship may exist between either or both of the first client device 208(1) and the second client device 208(2) and the ISF device 202, or no relationship may exist. For example, the ISF device 202 and the first client device 208(1) may be configured as the same physical device.

Further, ISF device 202 is illustrated as being able to access a microservice data repository 206(1) and a user-specific identification information database 206(2) The interaction services routing and handling module 302 may be configured to access these databases for implementing a method for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results.

The first client device 208(1) may be, for example, a smart phone. Of course, the first client device 208(1) may be any additional device described herein. The second client device 208(2) may be, for example, a personal computer (PC). Of course, the second client device 208(2) may also be any additional device described herein.

The process may be executed via the communication network(s) 210, which may comprise plural networks as described above. For example, in an exemplary embodiment, either or both of the first client device 208(1) and the second client device 208(2) may communicate with the ISF device 202 via broadband or cellular communication. Alternatively, the process may be executed by the ISF device 202 in a standalone manner, e.g., by a smart phone on which the interaction services routing and handling module 302 has been downloaded. Of course, these embodiments are merely exemplary and are not limiting or exhaustive.

Upon being started, a processor that is hosted in the ISF device 202 executes a process for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results. An exemplary process for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results is generally indicated at flowchart 400 in FIG. 4.

In process 400 of FIG. 4, at step S402, the interaction services routing and handling module 302 receives, from each of a plurality of users, a respective request for a corresponding interaction. At step S404, the interaction services routing and handling module 302 obtains request-specific information that relates to each respective request and user-specific information that relates to each respective user. In an exemplary embodiment, the interaction services routing and handling module 302 prompts each user to enter the user-specific information via a graphical user interface that is displayed on the screen of a client device 208.

Further, the interaction services routing and handling module 302 may also display, on a screen of the IDF device 202, a user interface for handling an interaction request that includes at least a subset of the request-specific information and at least a subset of the user-specific information. For example, referring to FIG. 5, a first screenshot 500 that illustrates a user interface for handling a customer interaction may include a task bar at the top of the screen, a trapezoidal-shaped ribbon that includes request-specific information and user-specific information at the top right-hand portion of the screen, a menu and a list of recent interactions along the left side of the screen, and status information relating to the current interaction request in the body of the screen. As another example, referring to FIG. 6, a second screenshot 600 that illustrates the user interface may include more details of the user-specific information, together with the trapezoidal-shaped ribbon shown in FIG. 5.

At step S406, the interaction services routing and handling module 302 determines, for each interaction, a request type for each respective request. The request type may indicate a communication mode by which a particular request is received. In an exemplary embodiment, the request type may include at least one of a voice request, an email request, an online chat request, a browser request, and a click-to-call request.

At step S408, the interaction services routing and handling module 302 analyzes, for each requested interaction, the request-specific information in order to determine at least one corresponding microservice and/or at least one microservice instance that is usable for handling the interaction. In an exemplary embodiment, the interaction services routing and handling module may determine more than one such microservice. For example, there may be any number of microservices that are suitable for handling different aspects of an interaction, such as two (2), three (3), five (5), ten (10), twenty (20), fifty (50), one hundred (100), or more such microservices; and some of these may have overlapping functions. As another example, there may be multiple microservice instances, which refers to instantiating one particular microservice multiple times.

At step S410, the interaction services routing and handling module 302 determines at least one suitable route for transmitting the request-specific information and the user-specific information for each respective interaction to a respective destination that relates to the microservices determined in step S408. In an exemplary embodiment, for any given interaction, there may be more than one suitable route and more than one suitable destination, depending on the microservices to be used, and also depending on the order of using the microservices. As a result, the interaction services routing and handling module 302 may determine two or more suitable routes and/or two or more suitable destinations for a particular interaction. Then, at step S412, the interaction services routing and handling module 302 uses a metric that relates to workload distribution for selecting an optimum route; and at step S414, the interaction services routing and handling module 302 uses the optimum route for routing the information.

FIG. 7 is a diagram 700 that illustrates a plurality of microservices and corresponding routing paths for implementing a method for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results, according to an exemplary embodiment. As illustrated in FIG. 7, a large number of microservices may be available for handling a particular request with respect to an interaction, including microservices having the following descriptors: “resource state”; “attribution”, “event listener”; “auditor”; “warm channel transfer”; “qualification”; “resource assign”; “event processor”, “monitor”; “flow processor”; “channel adapters”, “rules processor”; “get customer journey”; “specialist login”; “get specialist profile”; “get contacts”, “get communication history”, “receive voice & video call”; “invoke automated chat”; “invoke social”; “auditor”; “invoke simple chat”, “invoke conversation (multimedia)”; set disposition”; and “get customer journey”.

Further, as also illustrated in FIG. 7 and in accordance with an exemplary embodiment, the microservices may be depicted in a honeycomb-type hexagonal pattern. In this manner, the analyzing of a particular interaction effectively breaks up the associated tasks into relatively small pieces that correspond to different microservices. In an exemplary embodiment, a cloud native microservices-based implementation, such as Apache Kafka, is used, and in this construct, the honeycombs communicate with one other via events. The use of such an implementation provides several advantages, including the following: 1) Events must arrive in the proper order and must be scalable. 2) By partitioning the interactions, there is a low latency with respect to increasing or decreasing the number of microservices to be used (further noting that lower processing latency may be achieved by increasing the number of microservice instances). 3) By virtue of the ordering and the scalability of events, the interaction services handling module 302 achieves a higher throughput, thereby speeding up processing. 4) Load balancing and caching of IP addresses also contributes to higher processing speeds 5) The ability to identify multiple redundancies in connections between microservices provides system resiliency and robustness. In an exemplary embodiment, events relating to a specific user session must be consumed in exactly the same order as the events were produced Events relating to multiple user sessions need not be consumed, relative to each other, in the order in which they were produced. Distinguishing between events relating to a specific user session and events relating to multiple user sessions in this manner may facilitate a greater parallel processing capacity.

At step S416, the interaction services routing and handling module 302 receives response information that relates to a respective response for each corresponding request. In this aspect, in many situations, the received response effectively concludes the interaction.

In an exemplary embodiment, a cloud native microservice approach for an omni-channel contact center is provided. This approach includes decomposed contract based microservices and a microservices-based event-driven architecture that resides in the cloud and is designed to have an elastic scale, high availability, and high resiliency, with a service level agreement (SLA) that is higher than 99.999%. The contact center is a real time (millisecond, sub-second latency) architecture that has an extensive intrinsic design. Groups of microservices are created in order to provide different aspects of functionality. The stack includes a platform as a service (i.e., microservices platform, such as, for example, Kubernetes or Cloud Foundry), Kafka scalable event messaging and streaming technology, Cassandra, NoSQL performant private database for microservices, and distributed in-memory grid technologies such as, for example. Cloud Cache, for storing quickly accessible state information.

The general architecture includes a facade layer of microservices adapting to external vendor elements through predetermined protocols, and normalizing the communication to fit a highly available, concurrent processing, resilient, large-scale, event-based communication, Kafka Topics for ordered events to consuming instances of microservices; client-facing microservices which consume raw Kafka events from façade microservices and provide discrete functional services with a client-facing application programming interface (API)—RESTful Web Services, a general purpose notification service that provides a bidirectional low latency event exchange mechanism between clients (e.g., single user web clients) or server applications (e.g., fraud ecosystems, voice biometric systems, analytics, and/or recording systems); web clients following microservices architecture with user interface (UI), software development kit (SDK), and Services architecture using Angular8 frameworks, drop-in concept for specialist phone control applications into various servicing applications delivering a computer telephony integration (CTI) container with all of the functionality included therein; programmatic APIs for screen pop, and standalone ribbon. Clusters of microservices are provided for core servicing fabric telephony and agent login; automated specialist provisioning across multiple vendor solutions for orchestration, routing, recording, voicemail, and other functionalities; specialist phone control; and real-time dashboard for contact center supervisory personnel.

In another exemplary embodiment, a client ribbon embedding mechanism that is suitable for a large scale deployment and integration with key value pairs (KVPs) for screen pops is provided. The client ribbon embedding mechanism includes a self-contained feature set that is extensible to omni-channel without requiring extensive deployment and knowledge of CTI protocols and APIs by non-contact center developers. The mechanism creates a lightweight approach to integrating contact center specialist features into the servicing application, thereby providing a quicker rollout, reduced integration effort, and automatic updates for easier maintenance. The mechanism includes standardized integration patterns and a cookbook recipe approach, and provides a way to obtain integrated features required by servicing applications. These features may include: screen pops; updating customer relevant data; end call tracking; state change tied to case disposition; transfer and conference events; customized call notifications; and enabling key value observers (KVOs) to be updated by servicing applications, middleware, and fraud authentication systems.

In yet another exemplary embodiment, a Kafka usage for convening stateful ordered events to stateless, scalable eventing in real time is provided. The design includes concurrent data-center (DC) and pool-specific active and backup topics on multiple Kafka clusters in order to handle catastrophic pool failures. In an exemplary embodiment, a pool refers to an instance of the cloud platform so that multiple pools within a DC provide resiliency in the event of a failure of a single pool (e.g., a bad network router). In the present disclosure, a “pool” is equivalent to an Availability Zone (AZ) within a DC, and as such, the terms “pool” and “AZ” are used interchangeably herein. Other features include cross-DC Kafka events to provide a telephony service that is abstracted from an affinity to one of many DC's. The use of a Kafka routing key that is tied to directory numbers (DNs) and design in partitioning may also be provided, in order to cause ordered events to go to particular consumers in a scalable manner. A sticky Kafka partition assignor to reduce latencies when the cloud system automatically scales up or down may also be provided, for overcoming a need to rebalance and/or resend on multiple hops that may otherwise introduce latencies. A sequential thread executor may also be provided to distinguish between events that may be processed in parallel from those that must be processed sequentially.

The Kafka usage may include a sticky pool-aware Kafka partition assignor to enable a cloud system to automatically scale up or down despite pool affinities, which require each message to be processed by an instance within that pool that would otherwise fail or be inefficient outside of that pool. The sticky pool-aware Kafka partition assignor is designed to minimize churn while allowing an application to reserve a partition in order to avoid any impact while scaling up. The sticky pool-aware Kafka partition assignor may also cause partitions to stick to respective pools so that affinities to each pool are unaffected during rebalancing.

The Kafka usage may also provide for handling affinities at the edge of the cloud where only one instance can process a particular message but Kafka has only crude routing capabilities. In this aspect, an application instance with an affinity, such as, for example, a web-socket to a specific client, supplies the client with a subscription ID that happens to also be a Kafka routing key that guarantees that all messages sent to that client from back end services arrive, within a single hop, at the correct application instance. The application had previously reserved a partition, calculated as at least one universally unique identifier (UUID) that routes to the partition, so that the UUID(s) can be offered on demand to clients as subscription IDs.

The Kafka usage may also provide for multi-threading of the consumption of messages per Kafka partition while maintaining strict message ordering. In this aspect, for the vast majority of application, ordering only has meaning for messages produced with the same routing-key. Thus, the Kafka usage may be designed to process all messages received from a partition in parallel except for those messages with the same key which must be processed sequentially.

In still another exemplary embodiment, resiliency patterns and a client discovery service designed to overcome global load balancer (GLB) latencies is provided. Browsers and client desktops cache domain name system (DNS) resolution of uniform resource locators (URLs), and when the backend services or pools experience failures, the clients continue to attempt to generate requests to the same defunct destination. In such deployments, where no performant IP sprayers or gateways exist and where millisecond latency SL As exit, there may be a disruption in the continuous availability of services. In this aspect, a client side resiliency that complements the multi-pool, multi-instance, and multi-data center availability for instant seamless connection is provided. The client first discovers services and capabilities, including backup pool URLs, according to current availability and user authorization. The discovery service provides intelligent backup URLs for stateful services, stateless services, and external server systems. A client software development kit abstracts the resiliency, rehydration, and reconnection logic, begins network recovery, and then does a seamless login. The client user interface automatically recovers from the loss of a websocket or failure of a cloud microservice in a pool.

In yet another exemplary embodiment, resiliency patterns and seamless resiliency of stateful, low latency telephony clients across multiple data centers (DCs). In each data center, stateful edge services monitor each extension (i.e., domain name) simultaneously from different instances on both pools, thereby providing both instance and pool resiliency. Such services may use a de-duper that receives events from both pools but propagates only one pool. For phone resiliency, extension (domain name) may move from one data center to another, and the servicing fabric in both data centers may detect the move and direct requests to the new data center. Failure to login causes a resynchronization of the phone state in both data centers, thus self-healing in case discovery becomes out of synchronization.

The following table provides a list of features and specific aspects thereof:

Stateful Stateful→Stateless Bidirectional Dealing with Vendor Egress Follow the Phone - DR Domain WebSocket High Affinity connections failover Low Latency Minimize Latencies through Select Blazing Highly concurrent connections: Custom Sticky Kafka colocation Fast Technologies vendor systems & clients Partition Assignor Stack HA Provide High Availability Leverage nascent Event Starters encapsulate Standby Data Center (DC) (HA) of CaaS, Kafka clusters resiliency in stack High Availability (HA) Promotion under the cover Load Circuit Breaker Patterns: Connection to Global Phone and queue monitoring Data extractions load Balancing for end-user client and Load Balances (GLBs) load balanced across a DC balanced across Data server-to-server (API2API) for non-cloud servers Centers (DCs) invocations, with backup Availability Zones Black Client Side Recovery Kafka moves all load Subscriptions replicated SDK connects to other Availability (Web Socket disconnect, to other Availability across Availability Zones Availability Zone Zone Failure Availability Zone failure, Zone in less than 3 sec app failure) Grey AZ aware Sticky Partition Multiple layers of OAUTH2 Authorization Cloud Config Server has all Availability Assignor isolates network defense for grey across multiple Availability the bootstrap info, Prod: Zone Failure issues in Availability Zones failures Zone environment Bitbucket

In still another exemplary embodiment, defense mechanisms for handling grey failures in the cloud are provided. A first defense mechanism is a sticky partitioner that is designed to handle a scenario in which one pool is bad, and even while sharing the same Kafka and Cassandra across two pools, events would zigzag across applications in the two pool, thereby increasing the probability of a grey failure when any microservice in a second pool begins to go had, and also affecting all traffic. The sticky partitioner addresses this scenario by isolating network issues in pools by primarily routing the events to the same pool, thereby ensuring that 50% of the traffic is not affected by an unhealthy grey pool.

A second defense mechanism is the use of multiple levels of defense for grey failures so that a single failure does not equate to a request failure as it is retried across other pools and/or other mechanisms. For example, for a scenario in which an external server application issues a request to a pool that is only partially able to service the request, thereby resulting in a failure, this defense mechanism is designed to propagate all information available for servicing the request in a second attempt on another pool. If the second pool is able to find the remaining missing data from the first pool, then the second pool processes the request.

A third defense mechanism is the use of multiple layers of defense for grey failures for stateful applications so that a single failure does not equate to a request failure as there are multiple resiliency designs at each stage of the microservice in order to ensure servicing the request. For example, for a scenario in which a ribbon login fails because a CTI extension monitoring had failed or was interrupted, or because the request was routed to the wrong pool, or because the domain name is not in service, this defense mechanism is designed to perform several functions, including the following: CTI monitors domain name changes at all times; domain name in-service and out-of-service events are propagated across both data centers; if the login attempt comes to a data center where the domain name is out of service, CTI will ask the other data center's CTI to publish if the domain name is in service in that data center; repeat a set up from scratch for failed connections for some CTI domain names; delegate some failed connections for some CTI domain names from one CTI to a backup CTI; and recovery code in ribbon client to go into retry mode and determine when the domain name status changes, thereby self-healing.

In yet another exemplary embodiment, high efficiency reliable bidirectional messaging for low latency applications is provided. This embodiment includes several features A first feature is an ability to send a Kafka event direct to the instance hosting the web-socket for the final leg of delivery with a minimum possible latency. This is achieved by calculating a UUID that maps to a partition owned by the notification-service instance so that all messages sent using that UUID as a Kafka routing key are delivered directly to the correct one of many notification-service instances.

A second feature is an ability to scale up a number of instances without any latency nor disruption to existing web-socket users. This is achieved by using a custom stick partition assignor whereby the consumer is guaranteed that one partition is never removed. This also avoids two-hop routing.

A third feature is load balancing of system-wide events to another ecosystem through stateless, load balanced, randomized delivery on any of the web-sockets (WS) This feature provides an ability to load-balance events that can be consumed by a group of web-socket clients. This is achieved by allowing each member of a load-balancing (LB) group to subscribe with the name of the LB group so that future messages received by a notification service on a UUID that belongs to the group can be delivered to any member.

A fourth feature allows for more than one web-socket to be part of a high availability (HA) group to ensure low latency and guaranteed delivery on a surviving web-socket. This feature provides an ability to support clients that require a highly available pair of web-sockets where ordered events are delivered via an “active web-socket” only, and when it fails, the surviving web-socket is immediately promoted to being active. Thus, a latency that would have occurred without the HA group is completely avoided. Meanwhile, the client will initiate a new backup web-socket. To protect against failure or down-scaling, upon receiving a new web-socket request with an HA group identification, the corresponding notification service will reject a request to create a second web-socket in the same HA group on the same instance.

A fifth feature provides an ability to support message delivery from clients in multiple pools. This is achieved by using Kafka's native ability to route messages using a routing key so that the producer of the message only needs to know the Kafka cluster address.

A sixth feature provides an ability to subscribe anywhere, replicate everywhere, and notify anywhere. This feature further provides an ability to support message delivery from clients in multiple data centers (DCs) whereby when a message is received in one DC where the UUID is not recognized, the notification service will query a database to determine the Kafka cluster associated with the UUID so that the message is delivered in a second hop. In this manner, the client need not be concerned with the DC affinity of the web-socket.

A seventh feature provides an ability to act as a durable message provider by which no messages are lost. This feature further provides an ability to cache events in case a client is temporarily absent, providing a fire and forget service for microservices. This is achieved by caching undeliverable events for a configurable amount of time after a web-socket disconnects. On reconnection, the client will present, via a web-socket message, an identifier that maps it to the previously used UUID, and the notification service will then deliver all cached messages before continuing with normal message delivery.

An eighth feature provides a client side home pool, which allows clients to receive events more quickly by directing them to a more efficient pool. The efficiency is improved through locality, speedier delivery of events for co-located microservices, and Kafka, together with vendor gear for a particular user.

A ninth feature provides a common utility framework to notify any client independent of any type of microservices (i.e., a sender of an event). The common utility framework manages the client notification channel and is a common utility for services, thus abstracting them from the delivery details.

A tenth feature provides client session management via termination lifecycle events, which are being sent to all microservices. An eleventh feature provides abstracting of the Kafka resiliency architecture (e.g., dual DC or standby DC) via a mere web-socket delivery.

Taken together, these features provide additional advantages, including the following: First, ribbon clients were preferred not to talk to Kafka because it would require a partition for each user, but an excessive number of partitions would not be supported by Kafka, because of a lack of scalability, or else users would receive events that were intended for other users. Second, web-sockets are used for low latency, but the present embodiment uses a common web-socket towards a client, and routes all events from various microservices on the same channel.

In an exemplary embodiment, a ribbon is a web-based phone for contact center specialists to manage their state, control their physical phone (i.e., third party call control), perform telephony operation (i.e., basic or advanced) or be a true softphone (i.e., terminating media, e.g., audio in the web application) itself. The ribbon also provides a host of other contact center functionality.

In an exemplary embodiment, the ribbon is embeddable in a servicing application that corresponds to a line of business. In this aspect, a servicing application may include an application that a business uses to process customer transactions.

In an exemplary embodiment, the Ribbon is a cloud-based, elastically scalable, always-available web application built as a microservice, running with multiple instances in each pool, multiple pools in a data center (DC), and multiple DCs. A client is created as a stateless client, without any session affinity. The Ribbon is powered by a set of cloud native microservices following best practices. The Ribbon can be invoked by calling a well-defined global load-balanced web Uniform Resource Locator (URL) address.

The Ribbon is an angular modern web application that has three layers: 1) a user interface (JI) layer with HTML/CSS3 and UI layout packages, 2) a JavaScript software development kit (SDK) that abstracts the business logic, and resiliency; and 3) service wiring to microservices via RESTful web services and web socket APIs of (HTTPS/REST+JSON and WSS+JSON). The Ribbon should have diagnostics and monitoring like any other microservices. The Ribbon provides an automatic seamless login. The Ribbon is a web component—a widget that can be dropped into a web page or a web component in a thick (e.g., Visual C++/C#/Visual Basic) application.

The Ribbon is itself a mini-container of several features, including UI, corresponding JavaScript logic, and invocation of microservices. In an exemplary embodiment, the Ribbon is a composite GUI microservice that includes the following: 1) User Status—a microservice that maintains agent state and channel activity state, 2) Profile—a microservice that maintains agent profile (i.e., schedule, routing attributes, channels, presentation, operating profile, and basic parameters common to a business group); 3) Discovery—a microservice that can be used for a client to know what services are available and discover their URLs; 4) Call—a microservice that is responsible for incoming (and outgoing) calls (i.e., audio first and then video), 5) Notification—a microservice that is used to establish a web socket for events; 6) Queues display queue statistics applicable to a specialist; and 7) Obtain team listing and hierarchy details.

The Ribbon provides new features in a self-encapsulated way, thus not requiring changes on the servicing application. This can be expanded to new channels such as video, audio, chat, and/or any other suitable type of channel. The Ribbon can be embedded in a servicing application with a simple wiring mechanism as further described in a “cookbook.”

The cookbook prescribes the steps that a servicing application needs to perform in order to integrate with the Ribbon. The integration works for web applications as described below. For thick applications, such as, for example, VC++. VB or VC # applications, a bridge application is built between the thick application and a web component where the Ribbon will be displayed. The bridge allows bidirectional event passage (e.g., incoming call events and call metadata).

Referring to FIG. 8, a diagram 800 illustrates an anatomy of the Ribbon. The diagram 800 shows the specialists and supervisors using servicing applications to assist customers There can be many different kinds of servicing applications that run on the specialist's desktop. The diagram 800 depicts a web widget referred to herein as the Ribbon, which runs inside the servicing application. The Ribbon is composed of two layers. The first layer is the UI layer, which contains the presentation elements such as HTML5, CSS3, and layout packages and images. The second layer is a JavaScript SDK.

The SDK is a JavaScript library that the Ribbon uses to encapsulate the connections to the microservices and the connections to the eventing channel, i.e. web socket. The SDK also houses most of the business logic, and is responsible for the Ribbon user's authentication and seamless login, as well as recovering from network glitches and providing resiliency by connecting to alternative service locations. The SDK has JavaScript packages for each feature that the ribbon may need.

The SDK contains the following functionalities. 1) Initialize the SDK for the Ribbon; 2) establish connections to the microservices by first performing discovery check and then wiring up each feature to the back end service in the appropriate pool; 3) allows events to be sent to servicing applications for letting them know if the specialist is Ribbon enabled (i.e., during migrations), 4) once logged in, the SDK monitors health of connection from the Ribbon client to the server via the web socket channel and sends keep alives; 5) the SDK also provides logging functionality and utilities such as parsers; 6) events to indicate when a call has ended, and that the account/case needs to be wrapped up; and 7) to know when a transfer or conference has been established.

The SDK is also included in the servicing application, which provides a way for the servicing application to get events from the Ribbon (in turn from the Notification microservice), such as getting an incoming call with attached data that can be used to bring up a matching account in the servicing application, also known as screen pop. The SDK exposes an API that has simple methods for a servicing application developer to have just the required integration, without deep knowledge of the telephony operations, or even the RESTful web services nor the intricacies of the asynchronous web socket events. The SDK also makes easy to use JavaScript methods available for the servicing application to invoke aspects to be used in an integration process as further described below.

The SDK is also the bridge between the Ribbon and a servicing application for events and for functionality that the servicing application can programmatically invoke (i.e., an extension of the ribbon functionality). A servicing application that embeds the Ribbon can instantiate the SDK and subscribe to events. Once a call comes in, new metadata associated with the call can be received from the SDK. The call's metadata may be updated by calling the SDK. Invoke a specialist state change to after-call work if the case is still being worked on even after the call. Switch agent's state back to ready when a case is closed. Make an outbound call to a predetermined destination. The SDK is loaded at run time and can be updated dynamically, thus keeping it updated independently while staying backward compatible with the APIs.

Ribbon Sequence of Invoking Servicing Fabric Microservices:

The Ribbon is a web container that provides extensible set of features, such as Profile, State management, Visual Voicemail, Dial Pad, Speed Dials, Call Operations and Queue information. This can be extended to other Omni channel features such as Chat, Video calls, Social, Email, CoBrowse, Address Book, Favorites, Call History and Authentication, and Workforce optimization related features. The Ribbon web application itself is a stateless cloud native microservice deployed in multiple availability zones and data centers fronted by a global load balancer. Each of these features is supported by a microservice that is specific to the feature and hence provides extensibility and a full stack approach for the complete stack (i.e., UI to web services and backend integrations required for that web service). Referring to FIG. 9, the Ribbon is self-contained in that it initializes and activates all required services it requires, as illustrated in a diagram 900.

The Ribbon loads and executes a high level sequence as described below:

1) Invoke Discovery service (i.e., REST web service exposed by the Discovery microservice) which returns data about whether the specialist is enabled for specific features, and the remaining microservice URLs. For each there is a fallback set of URLs as well in order for the client to have resiliency in case there is failure on the primary default URLs. Preferred service URLs are provided based on the extension number which the specialist is using in order to have the lowest latency communications possible, with fallbacks to other availability regions having identical microservices with connections to vendor systems.

2) The next step is to invoke and fetch the profile of the specialist (i.e., with seamless authentication) that allows the Ribbon to show the photo and profile details of the specialist.

3) One of the microservices revealed by the discovery service is the notification microservice's URL, i.e., a low latency web socket communication channel service to which URL, a web socket is established.

4) Login process is initiated, which then results in loading and activating the enabled features in the Ribbon. For example, if calls are enabled, the dial pad, speed dial, queues and related features are displayed.

5) Telephony features such as making a call, answering a customer's call, and reviewing attached data, and performing basic telephony operations such as hold/unhold, mute/unmute and disconnecting are all contextually available when a call is active. Advanced operations such as consultative and blind transfers and conferences, participant actions and timers are also available.

6) Operations are invoked through secure web services (i.e., HTTPS/REST+JSON) and asynchronous events are received through the web sockets as WSS/JSON messages, which the Ribbon receives and updates the internal state machine, call context and the UI.

7) Voicemail alerts and queue metrics are also continuously updated when JSON messages are received through the web socket channel.

The Web socket connection follows the following steps:

1) Using the notification URL, the SDK initiates a web socket connection to the backend and receives a unique notification identifier that comes closest to representing an active client session, which is only needed for the event subscriptions.

2) Based on the discovery service response, the Ribbon proceeds to subscribe to events from various services such as Call Microservice (i.e., call events), User Status Microservice (i.e., state change and login, logout events) and Presence Microservice (i.e., queue statistics such as number of calls in queue, oldest call waiting, and number of available agents) and Voicemail events (i.e., newly deposited or read/deleted voicemails).

3) The event subscription is terminated when the functionality is not needed, such as, for example, when the queue events are not being displayed, or at the time of logout from the Ribbon.

Regarding integration: Unlike most contact center solution vendors, where the vendor supplies a separate desktop application that provides telephony operations for a specialist, the Ribbon integrates into several contact center servicing applications with an easy integration. From the view of a servicing application that can be a web application constructed using older or modern technologies and frameworks, those that are built on top of vendor frameworks like a PEGA based web application or even thick windows clients written using Visual C#, Visual Basic or older applications, the following process facilitates an easy integration.

1a) The servicing application invokes the Discovery Microservice and evaluates whether the servicing application should show the new Ribbon if the agent has migrated over (i.e., isRibbonEnabled=true), else follow the pre-Ribbon methodology of CTI control.

1b) Alternatively, some servicing apps instantiate the SDK, subscribe to events, and begin the initial load of the Ribbon that does the discovery check.

2) If isRibbonEnabled=true, then the Servicing application continues the load of the ribbon HTML/CSS3 as a web component inside its main web page (i.e., usually anchored near the menu bar at the top of the page). Some servicing applications create a child window within the application and load the Ribbon as a web component inside that window.

3) The Ribbon application during its load follows the sequence intrinsic to the Ribbon and establishes the web socket notification.

4) The servicing application receives incoming call events and then proceeds to invoke its screen pop logic, such as, for example, filter out the metadata for specific customer information and match it with the servicing application's database and pop up a matching account/case.

5) When a call ends, the servicing application receives an end call event from the SDK and allows the specialist to wrap a case and close the matching account.

It is noted that if the servicing application is a thick application (i.e., non-web), then one approach is to create a bridge application that will pass events back and forth between the web components and the legacy thick application.

Advanced integrations include the following:

1) Servicing applications synchronize the state of the agent to the state of the case that they are working on, for example as soon as an incoming call is ringing or answered by the specialist, the servicing application uses the SDK API to change state of the agent to After call work to indicate that the specialist is busy on the case and another call should not be presented to the specialist. Only when the specialist decides to close the case, will the servicing application again invoke the SDK API and change the agent's state to ready. Thus there are further economies by the symbiotic relationship between the servicing application and the SDK events to save Average handle time by automatic creation of a case, automatic changing to ACW and automatic change to Ready.

Another advanced step is to watch for consultation calls or a conference merge and bring up the appropriate customer's case. Yet another functionality is to enable Dial buttons in the servicing application when the specialist is not on a call. Advanced applications would want to change the metadata based on specific flows and call the SDK API to add/update metadata. Some apps also begin a transfer to a specified destination.

Referring to FIG. 10, diagram 1000 illustrates shows a simplified sequence of steps to be performed by an integrating servicing application. The Ribbon self-encapsulates all the complex logic, and the servicing application integration points are only those that are most meaningful to the application's workflow. This lessens the effort, cost and complexity of integrating the Ribbon.

In an ADFS Login step, the servicing application ensures that authentication credentials and/or a token can be passed to the Ribbon and for application programming interfaces (APIs). In a “Svc Discovery, Ribbon User?” step, the servicing application checks whether an agent has discovered the Ribbon URL. In an Establish Fixed Ribbon Location step, the servicing application establishes a fixed location in its page for the Ribbon. In a Launch Embedded Ribbon step, the servicing application adds code to embed the Ribbon and points to the URL Finally, in a “Check Screen Pop, Toaster, Dial Pad” step, the servicing application verifies the Ribbon functionality and placement of toasters and popups.

Accordingly, with this technology, an optimized process for handling large number of customer service interactions to ensure efficient and accurate interaction servicing results is provided.

Although the invention has been described with reference to several exemplary embodiments, it is understood that the words that have been used are words of description and illustration, rather than words of limitation. Changes may be made within the purview of the appended claims, as presently stated and as amended, without departing from the scope and spirit of the present disclosure in its aspects. Although the invention has been described with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed, rather the invention extends to all functionally equivalent structures, methods, and uses such as are within the scope of the appended claims.

For example, while the computer-readable medium may be described as a single medium, the term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” shall also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the embodiments disclosed herein.

The computer-readable medium may comprise a non-transitory computer-readable medium or media and/or comprise a transitory computer-readable medium or media. In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random-access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. Accordingly, the disclosure is considered to include any computer-readable medium or other equivalents and successor media, in which data or instructions may be stored.

Although the present application describes specific embodiments which may be implemented as computer programs or code segments in computer-readable media, it is to be understood that dedicated hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement one or more of the embodiments described herein Applications that may include the various embodiments set forth herein may broadly include a variety of electronic and computer systems. Accordingly, the present application may encompass software, firmware, and hardware implementations, or combinations thereof. Nothing in the present application should be interpreted as being implemented or implementable solely with software and not hardware.

Although the present specification describes components and functions that may be implemented in particular embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions are considered equivalents thereof.

The illustrations of the embodiments described herein are intended to provide a general understanding of the various embodiments. The illustrations are not intended to serve as a complete description of all the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.

One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.

The Abstract of the Disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as defining separately claimed subject matter.

The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims, and their equivalents, and shall not be restricted or limited by the foregoing detailed description. 

What is claimed is:
 1. A method for managing contact center interactions, the method being executed by at least one processor, the method comprising: receiving, by the at least one processor from a servicing application, a request for a web application that implements a plurality of contact center functions; integrating, by the at least one processor, the web application into the servicing application; and displaying, by the at least one processor, a ribbon that includes information that relates to each of the plurality of contact center functions, wherein each of the plurality of contact center functions is implemented as a respective cloud native microservice, and wherein the web application includes a JavaScript software development kit that connects each respective cloud native microservice to a transaction processing application, and wherein the method further comprises using the JavaScript software development kit to manage connectivity to cloud microservices and to propagate received events to the servicing application.
 2. The method of claim 1, further comprising embedding the ribbon in a user interface screen of the servicing application.
 3. The method of claim 2, wherein the ribbon is displayed in a section of the user interface screen that is positioned adjacent to a task bar of the servicing application.
 4. The method of claim 1, wherein the plurality of contact center functions includes at least three from among a user status function that maintains an agent state and a channel activity state, a profile function that maintains agent profile information, a discovery function that provides information relating to available services and corresponding Uniform Resource Locators (URLs), a call function that relates to incoming and outgoing telephone calls, a notification function that establishes a web socket for events, and a queue function that relates to queue statistics.
 5. The method of claim 1, further comprising: activating at least one feature that corresponds to the received event; and displaying, in the ribbon, a respective image that relates to each of the activated at least one feature.
 6. The method of claim 1, wherein when the received event is an incoming call, the method further comprises using the JavaScript software development kit to provide metadata associated with the call to the servicing application.
 7. A computing apparatus for managing contact center interactions, the computing apparatus comprising: a processor; a memory; a display; and a communication interface coupled to each of the processor, the memory, and the display, wherein the processor is configured to: receive, from a servicing application, a request for a web application that implements a plurality of contact center functions; integrate the web application into the servicing application; and display, on the display, a ribbon that includes information that relates to each of the plurality of contact center functions, wherein each of the plurality of contact center functions is implemented as a respective cloud native microservice, and wherein the web application includes a JavaScript software development kit that connects each respective cloud native microservice to a transaction processing application, and wherein the processor is further configured to use the JavaScript software development kit to manage connectivity to cloud microservices and to propagate received events to the servicing application.
 8. The computing apparatus of claim 7, wherein the processor is further configured to embed the ribbon in a user interface screen of the servicing application.
 9. The computing apparatus of claim 8, wherein the ribbon is displayed in a section of the user interface screen that is positioned adjacent to a task bar of the servicing application.
 10. The computing apparatus of claim 7, wherein the plurality of contact center functions includes at least three from among a user status function that maintains an agent state and a channel activity state, a profile function that maintains agent profile information, a discovery function that provides information relating to available services and corresponding Uniform Resource Locators (URLs), a call function that relates to incoming and outgoing telephone calls, a notification function that establishes a web socket for events, and a queue function that relates to queue statistics.
 11. The computing apparatus of claim 7, wherein the processor is further configured to: activate at least one feature that corresponds to the received event; and display, in the ribbon, a respective image that relates to each of the activated at least one feature.
 12. The computing apparatus of claim 7, wherein when the received event is an incoming call, the processor is further configured to use the JavaScript software development kit to provide metadata associated with the call to the servicing application.
 13. A non-transitory computer readable storage medium storing instructions for managing contact center interactions, the storage medium comprising executable code which, when executed by at least one processor, causes the at least one processor to: receive, from a servicing application, a request for a web application that implements a plurality of contact center functions; integrate the web application into the servicing application; and display a ribbon that includes information that relates to each of the plurality of contact center functions, wherein each of the plurality of contact center functions is implemented as a respective cloud native microservice, and wherein the web application includes a JavaScript software development kit that connects each respective cloud native microservice to a transaction processing application, and wherein when executed, the executable code further causes the processor to use the JavaScript software development kit to manage connectivity to cloud microservices and to propagate received events to the servicing application.
 14. The storage medium of claim 13, wherein when executed by the at least one processor, the executable code further causes the at least one processor to embed the ribbon in a user interface screen of the servicing application. 